Automatic Physical Access

ABSTRACT

Physical access to secure areas is automatically performed based on presence or detection of a wireless device. A unique identifier of a wireless cellular device, for example, may be pre-authorized for occupants, employees, and tenants of a building. Contractors and vendors may also have their wireless cellular devices pre-approved for access. When the wireless cellular device is detected by a network serving the secure area, its unique identifier may be compared to databases or lists of approved cellular devices. Physical access may thus be automatically granted, based on possession of a recognized cellular device.

CROSS-REFERENCE TO RELATED APPLICATION

This application is a continuation of U.S. application Ser. No.14/666,356 filed Mar. 24, 2015 and since issued as U.S. Patent X, andincorporated herein by reference in its entirety.

BACKGROUND

Secure physical access is important to homes and businesses. Much moneyand time are devoted to reducing rogue, criminal entry into homes andbusinesses.

BRIEF DESCRIPTION OF THE SEVERAL VIEWS OF THE DRAWINGS

The features, aspects, and advantages of the exemplary embodiments areunderstood when the following Detailed Description is read withreference to the accompanying drawings, wherein:

FIGS. 1-7 are simplified schematics illustrating an environment in whichexemplary embodiments may be implemented;

FIGS. 8-10 are more detailed block diagrams illustrating the operatingenvironment, according to exemplary embodiments;

FIGS. 11-12 are schematics illustrating a database of meetings,according to exemplary embodiments;

FIGS. 13-18 are schematics illustrating locational tracking, accordingto exemplary embodiments;

FIGS. 19-22 are schematics illustrating building services, according toexemplary embodiments;

FIG. 23 is a schematic illustrating elevator summons, according toexemplary embodiments;

FIGS. 24-25 are schematics further illustrating a database of calendars,according to exemplary embodiments;

FIGS. 26-29 are schematics illustrating historical network tracking,according to exemplary embodiments;

FIG. 30 is a schematic illustrating network tracking, according toexemplary embodiments;

FIG. 31 is a schematic illustrating an overall database scheme,according to exemplary embodiments;

FIG. 32 is a schematic illustrating cancelations, according to exemplaryembodiments;

FIG. 33 is a schematic illustrating conferencing activities, accordingto exemplary embodiments;

FIGS. 34-35 are flowcharts illustrating an algorithm for accessauthorization, according to exemplary embodiments; and

FIGS. 36-37 depict still more operating environments for additionalaspects of the exemplary embodiments.

DETAILED DESCRIPTION

The exemplary embodiments will now be described more fully hereinafterwith reference to the accompanying drawings. The exemplary embodimentsmay, however, be embodied in many different forms and should not beconstrued as limited to the embodiments set forth herein. Theseembodiments are provided so that this disclosure will be thorough andcomplete and will fully convey the exemplary embodiments to those ofordinary skill in the art. Moreover, all statements herein recitingembodiments, as well as specific examples thereof, are intended toencompass both structural and functional equivalents thereof.Additionally, it is intended that such equivalents include bothcurrently known equivalents as well as equivalents developed in thefuture (i.e., any elements developed that perform the same function,regardless of structure).

Thus, for example, it will be appreciated by those of ordinary skill inthe art that the diagrams, schematics, illustrations, and the likerepresent conceptual views or processes illustrating the exemplaryembodiments. The functions of the various elements shown in the figuresmay be provided through the use of dedicated hardware as well ashardware capable of executing associated software. Those of ordinaryskill in the art further understand that the exemplary hardware,software, processes, methods, and/or operating systems described hereinare for illustrative purposes and, thus, are not intended to be limitedto any particular named manufacturer.

As used herein, the singular forms “a,” “an,” and “the” are intended toinclude the plural forms as well, unless expressly stated otherwise. Itwill be further understood that the terms “includes,” “comprises,”“including,” and/or “comprising,” when used in this specification,specify the presence of stated features, integers, steps, operations,elements, and/or components, but do not preclude the presence oraddition of one or more other features, integers, steps, operations,elements, components, and/or groups thereof. It will be understood thatwhen an element is referred to as being “connected” or “coupled” toanother element, it can be directly connected or coupled to the otherelement or intervening elements may be present. Furthermore, “connected”or “coupled” as used herein may include wirelessly connected or coupled.As used herein, the term “and/or” includes any and all combinations ofone or more of the associated listed items.

It will also be understood that, although the terms first, second, etc.may be used herein to describe various elements, these elements shouldnot be limited by these terms. These terms are only used to distinguishone element from another. For example, a first device could be termed asecond device, and, similarly, a second device could be termed a firstdevice without departing from the teachings of the disclosure.

FIGS. 1-7 are simplified schematics illustrating an environment in whichexemplary embodiments may be implemented. FIG. 1 illustrates a humanuser 20 in a lobby 22 of a building 24. The human user 20 may be anemployee working within the building 24, or the human may be visitingsomeone within the building 24. The human user 20, in short, may be anemployee, a visitor, a contractor, a tenant, or a guest requesting entryinto the building 24. For simplicity, the human user 20 will mainly bedescribed as a visitor. When the visitor 20 wishes to enter an elevator26 and proceed into secure areas of the building 24, the visitor 20usually must check-in with a security guard. Here, though, exemplaryembodiments detect the wireless presence of the visitor's mobile device30, such as her smartphone 32. That is, if the visitor's smartphone 32is recognized, then exemplary embodiments may permit entry of thevisitor 20 to the secure areas within the building 24. However, if thevisitor's smartphone 32 is unrecognized, then exemplary embodiments mayrequire more authentication credentials or additional measures, as laterparagraphs will explain.

FIG. 2 illustrates wireless presence. When the visitor enters some area(such as the lobby 22 or other area of the building 24), the visitor'ssmartphone 32 may attempt to access a wireless network 40 serving thelobby 22. As the reader likely understands, many people carry asmartphone that interfaces with wireless networks. So, when thevisitor's smartphone 32 enters the lobby 22, the smartphone 32 mayestablish wireless communication with the wireless network 40 servingthe lobby 22. The smartphone 32, for example, may request access orpermission to a local area wireless fidelity (or WI-FI®) network servingthe lobby 22 or any other area.

A security server 42 may be consulted. Once the wireless network 40detects the radio presence of the visitor's smartphone 32, the securityserver 42 may determine whether the visitor 20 is authorized for entry,based on the wireless presence of the visitor's smartphone 32. Forexample, the security server 42 may consult a database 44 of personnel.The database 44 of personnel may store names, addresses, and/or otherinformation for personnel who are authorized to enter the secure area ofthe building 24. The database 44 of personnel, however, may be arrangedaccording to mobile devices. That is, the database 44 of personnel maystore database associations between different names or identities ofpeople and different unique identifiers of their mobile devices. If anentry in the database 44 of personnel matches the unique identifier ofthe visitor's smartphone 32, then the corresponding visitor 20 isauthorized to enter the building 24. Employees and tenants may thusquickly and easily enter the building 24, merely based on wirelessrecognition of their mobile devices 30.

FIG. 3 further illustrates secure access. If the smartphone 32 is notmatched to the database 44 of personnel, the visitor may still begranted access for legitimate purposes. For example, the visitor may bea supplier or contractor attending a meeting within the building 24.When the wireless network 40 detects the frequency presence of thevisitor's smartphone 32, the security server 42 may consult a database46 of meetings. The database 46 of meetings stores different meetingsthat are scheduled or calendared within the building 24. Each meetingmay have an associated list 48 of invitees who are authorized to attendthe meeting. Each invitee, however, may be identified according to hisor her mobile device 30. That is, each invitee may be identified by aunique cellular identifier associated with, or assigned to, theircellular mobile device (such as the smartphone 32). The database 46 ofmeetings may thus store database associations between differentscheduled meetings and different unique identifiers of the invitees'mobile devices 30. If an entry in the database 46 of meetings matchesthe unique identifier of the visitor's smartphone 32, then thecorresponding human visitor may be authorized for entry to attend thecorresponding meeting. Supplier personnel, contractors, and otherinvitees may thus quickly and easily enter the building, based onwireless recognition of their smartphones 32.

FIG. 4 further illustrates the database 46 of meetings. Here inviteesmay be more limited in the dates and times of their access. As FIG. 4illustrates, each meeting 50 may also be associated with a date 52, astart time 54, and a duration 56. Even though the visitor's smartphone32 may be matched as an invitee to the meeting 50, the visitor may stillbe denied access. For example, when the visitor's smartphone 32 requestsaccess to the wireless network 40, a current date and time 58 may betime stamped. If the current date and time 58 does not match thescheduled date 52 of the meeting 50, then entry may be denied.Furthermore, if the smartphone 32 requests wireless access (to thewireless network 40) too early or too late for the scheduled meeting 50,then entry may be denied. The scheduled meeting 50 may thus have awindow 60 of arrival, before or after which the visitor may not enter.So, even though a supplier or contractor is authorized for entry,admittance may be limited to nearly the scheduled date 52 and start time54 of the meeting 50. The user of the smartphone 32 may thus beauthorized for physical entry, but exemplary embodiments may requirethat the user wait until the window 60 of arrival is satisfied.Similarly, when the meeting 50 ends (perhaps at a stop time calculatedusing the duration 56), the visitor's smartphone 32 may not linger.Exemplary embodiments may thus continue tracking the smartphone 32 (aslater paragraphs will explain) during and after the meeting 50 to ensurethe visitor does not afterwards linger too long. If the attendingvisitor lingers too long after the meeting 50, exemplary embodiments maydeny exit from the building, as a security precaution.

FIG. 5 illustrates a database 70 of calendars. Here the visitor'ssmartphone 32 may be matched to an individual's electronic calendar 72.As the reader likely understands, many people maintain their electroniccalendars in a central location (such as an enterprise server database).The database 70 of calendars, in other words, stores differentelectronic calendars for different users (such as the employees and/ortenants in the building 24). When the wireless network 40 detects theradio presence of the smartphone 32, the security server 42 may querythe database 70 of calendars for the unique identifier of the smartphone32. If a matching calendar entry is determined, then the smartphone 32is calendared to meet an employee or tenant inside the building 24.Exemplary embodiment may thus authorize entry, based on wireless networkrecognition of the visitor's smartphone 32.

FIG. 6 illustrates notification. Once the security server 42 authorizesthe visitor's smartphone 32, electronic notifications may be sent. Thesecurity server 42 may thus generate and send one or more electronicmessages 80 to destination devices 82 associated with differentdestination addresses 84, thus alerting of the visitor's entry into thebuilding 24. An employee, for example, may be alerted to the visitor'sarrival. Other meeting invitees may also be notified, using the uniqueidentifier assigned to their respective smartphones.

FIG. 7 illustrates entry. Once the security server 42 authorizes thevisitor's smartphone 32, the corresponding visitor may enter the securearea. The security server 42 may thus generate an electronic entryinstruction 86 to allow physical entry. The entry instruction 86 is thensent as packets of data to any destination device. FIG. 7, for example,illustrates the entry instruction 86 routing to a network addressassigned to a lock controller 88. The lock controller 88 manages anelectronic lock 90 securing some door or gate. The entry instruction 86instructs the lock controller 88 to activate or unlock the electroniclock 90, thus allowing the visitor to physically enter the building 24and/or some floor within the building 22. The security server 42 mayfurther instruct an elevator controller 92 to summon an elevator 94,thus lifting the visitor to some floor or level, as later paragraphswill explain. The security server 42 may also monitor or track themovement of the visitor's smartphone 32 to prevent frolic orunauthorized detours (as later paragraphs will also explain).

Exemplary embodiments thus synchronize entry with wireless detection.Wireless detection of any mobile device 30 may thus be used to authorizeentry to secure areas. Even though FIGS. 1-7 primarily illustrate thevisitor's smartphone 32, exemplary embodiments may utilize any wired orwireless device (as later paragraphs will explain). Indeed, badges,watches, and other wearable smart devices may be wirelessly detected topermit access. Integration with personnel directories and calendaringsystems further defines permissible locations of visitors.

FIGS. 8-10 are more detailed block diagrams illustrating the operatingenvironment, according to exemplary embodiments. FIG. 8 illustratespresence detection of the visitor's smartphone 32. When the smartphone32 enters any area, the smartphone 32 may establish wirelesscommunication with the wireless network 40 serving the area. Thesmartphone 32, for example, may request access or permission to a localarea wireless fidelity (or^(WIFI)®) network, wide area cellular network,or any other network. The wireless network 40 may only recognize, ortransmit/receive, using a particular frequency or band. The smartphone32 may thus instruct its transceiver (not shown for simplicity) towirelessly request access permission using the electromagnetic frequencyband required by the wireless network 40.

The security server 42 may be notified. When the wireless network 40detects the smartphone 32, exemplary embodiments may inform the securityserver 42. That is, the smartphone 32 may send an access request to anaccess device 100 serving the wireless network 40. FIG. 8 illustratesthe access device 100 as a wireless router 102, which commonly servesmany residential and business WIFI® networks. However, the access device100 may be any network interface to an access network, such as agateway, cable modem, or DSL modem. Regardless, the smartphone 32broadcasts a request that seeks access permission to the wirelessnetwork 40. When the access device 100 receives the access request, theaccess device 100 may send a packetized access notification 104 into acommunications network 106 for routing and delivery to a network addressassociated with the security server 42. The wireless router 102, forexample, may store or execute code or programming that forces orcommands the access notification 104 when any device attempts to accessthe wireless network 40. The access notification 104 may thus alert thesecurity server 42 to the radio frequency presence of the visitor'ssmartphone 32. The access notification 104 may further includeinformation that uniquely identifies the smartphone 32, such as datarepresenting a cellular identifier 110. While any alphanumericcombination may uniquely identify the smartphone 32, FIG. 8 illustratesthe smartphone's cellular telephone number (or “CTN”) 112, InternationalMobile Subscriber Identity (or “IMSI”) 114, or Mobile StationInternational Subscriber Directory Number (“MSISDN”) 116. Whenever themobile smartphone 32 sends messages or information, the smartphone 32may include or self-report its CTN 112, IMSI 114, and/or its MSISDN 116.

The security server 42 may authorize the smartphone 32. The securityserver 42 has a processor 120 (e.g., “μP”), application specificintegrated circuit (ASIC), or other component that executes a securityalgorithm 122 stored in a local memory 124. The security algorithm 122instructs the processor 120 to perform operations, such as receiving andprocessing information received from a network interface to thecommunications network 106. The information may be received as packetsof data according to a packet protocol (such as any of the InternetProtocols). The packets of data contain bits or bytes of data describingthe contents, or payload, of a message. A header of each packet of datamay contain routing information identifying an origination addressand/or a destination address. The security algorithm 122, for example,may instruct the processor 120 to inspect the packetized accessnotification 104 for the cellular identifier 110 associated with thevisitor's smartphone 32 requesting access to the wireless network 40.

FIG. 9 illustrates the database 44 of personnel. The database 44 ofpersonnel may store names, addresses, images, and/or other informationfor personnel who are authorized to enter any area. For simplicity thedatabase 44 of personnel is illustrated as a table 130 thatelectronically maps, relates, or associates different employees ortenants 132 to their corresponding personal information. For example, anentry may associate each person's name 134, address 136, and/or employeenumber 138 to the cellular identifier 110 associated with the person'spersonal wireless device (such as the smartphone 32 illustrated in FIGS.1-8). FIG. 9 illustrates the cellular identifier 110 as the cellulartelephone number (“CTN”) 112, the IMSI 114, and/or the MSISDN 116. Eachperson's wireless device, however, may be additionally or alternativelyuniquely identified by a network address, a manufacturer's serialnumber, or any other alphanumeric combination. Moreover, the database 44of personnel may further associate a digital image file 140 to thecellular identifier 110, thus allowing retrieval, recognition, and/oranalysis of a facial image. The database 44 of personnel is illustratedas being locally stored in the memory 124 of the security server 42, butsome or all of the database entries may be remotely maintained at someother server or location in the communications network (illustrated asreference numeral 106 in FIG. 8). While FIG. 9 only illustrates a fewentries, in practice the database 44 of personnel may contain manyentries for hundreds or thousands of people.

The security server 42 may query the database 44 of personnel. Returningto FIG. 8, when the security server 42 receives the access notification104, the security algorithm 122 causes the processor 120 to query forentries that match the query search term(s) detailed or described in theelectronic access notification 104. If the database 44 of personnelcontains a matching entry, then the security server 42 may authorize thesmartphone 32 (and thus the corresponding user or visitor) to enter. Thesecurity server 42 thus recognizes the smartphone 32 as belonging to oneof the personnel authorized to enter the building (illustrated asreference numeral 24 in FIGS. 1-7). As an example, if the CTN 112, theIMSI 114, and/or the MSISDN 116 matches an entry in the database 44 ofpersonnel, then the security server 42 may conclude that thecorresponding user of the smartphone 32 is authorized to enter.

FIG. 10 illustrates the entry instruction 86. When the visitor'ssmartphone 32 is recognized, the security server 42 may automaticallyauthorize entry. The security algorithm 122 may thus instruct theprocessor 120 to generate the entry instruction 86 to allow physicalentry. The entry instruction 86 may contain any information thatconfirms the smartphone 32 is authorized to enter the secure area. FIG.10 illustrates the entry instruction 86 routing to the network addressassigned to the lock controller 88. The entry instruction 86 instructsthe lock controller 88 to activate or unlock the electronic lock 90. Thesecurity server 42 may thus unlock a door, gate, or turnstile thatpermits physical entry of the corresponding user of the smartphone 32.An employee or tenant thus enters based on the wireless recognition ofthe smartphone 32.

Exemplary embodiments thus present an elegant solution. In today'smobile environment, people may be uniquely identified by their mobiledevices (such as the smartphone 32). Employees, tenants, and visitorsmay thus be personally identified merely by carrying their smartphones.Exemplary embodiments may thus permit authorized entry to secure areas,simply by recognizing wireless transmissions from their mobile devices.No phone calls are needed, and labor expenses are reduced.

Exemplary embodiments may be applied regardless of networkingenvironment. Exemplary embodiments may be easily adapted to stationaryor mobile devices having cellular, WI-FI®, near field, and/or BLUETOOTH®capability. Exemplary embodiments may be applied to mobile devicesutilizing any portion of the electromagnetic spectrum and any signalingstandard (such as the IEEE 802 family of standards, GSM/CDMA/TDMA or anycellular standard, and/or the ISM band). Exemplary embodiments, however,may be applied to any processor-controlled device operating in theradio-frequency domain and/or the Internet Protocol (IP) domain.Exemplary embodiments may be applied to any processor-controlled deviceutilizing a distributed computing network, such as the Internet(sometimes alternatively known as the “World Wide Web”), an intranet, alocal-area network (LAN), and/or a wide-area network (WAN). Exemplaryembodiments may be applied to any processor-controlled device utilizingpower line technologies, in which signals are communicated viaelectrical wiring. Indeed, exemplary embodiments may be appliedregardless of physical componentry, physical configuration, orcommunications standard(s).

Exemplary embodiments may utilize any processing component,configuration, or system. Any processor could be multiple processors,which could include distributed processors or parallel processors in asingle machine or multiple machines. The processor can be used insupporting a virtual processing environment. The processor could includea state machine, application specific integrated circuit (ASIC),programmable gate array (PGA) including a Field PGA, or state machine.When any of the processors execute instructions to perform “operations”,this could include the processor performing the operations directlyand/or facilitating, directing, or cooperating with another device orcomponent to perform the operations.

FIGS. 11-12 are schematics further illustrating the database 46 ofmeetings, according to exemplary embodiments. Here the smartphone 32 maybe an invitee to a meeting within some secure area. When the wirelessnetwork 40 detects the radio presence of the visitor's smartphone 32,the access device 100 sends the access notification 105 to the securityserver 42. The packetized access notification 104 may include datadescribing the cellular identifier 110 (e.g., the CTN 112, the IMSI 114,and/or the MSISDN 116). The security server 42 may then query thedatabase 46 of meetings to determine if the smartphone 32 matches thelist 48 of invitees to any scheduled meeting 50.

FIG. 12 illustrates the database 46 of meetings. For simplicity, FIG. 12illustrates the database 46 of meetings being locally stored in thememory 124 of the security server 42. However, some or all of thedatabase entries may be remotely maintained at some other server orlocation in the communications network (illustrated as reference numeral106 in FIG. 11). While FIG. 12 only illustrates a few entries, inpractice the database 46 of meetings may contain many entries forhundreds or thousands of different meetings or gatherings. The database46 of meetings is illustrated as a table 150 that maps, relates, orassociates different scheduled meetings 50 to the corresponding list 48of invitees. While each invitee 48 may be identified by their name, hereexemplary embodiments identify each invitee 48 according to his or hermobile device identifier. That is, each invitee 48 may be identified bythe unique cellular identifier 110 associated with, or assigned to,their cellular device (such as the smartphone 32). FIG. 12 thusillustrates database associations between a meeting 50, an organizer orinviter 152, and the different invitees 48. Each party to the meeting 50may thus be uniquely identified by their respective CTN 112, IMSI 114,and/or MSISDN 116. Referring back to FIG. 11, if an entry in thedatabase 46 of meetings matches the unique cellular identifier 110associated with the smartphone 32, then the corresponding user may beauthorized for entry to attend the corresponding meeting 50. Thesecurity server 42 may thus authorize entry, such as by generating theentry instruction 86 (as illustrated with reference to FIG. 10).Supplier personnel, contractors, and other invitees may thus quickly andeasily enter the building, based on wireless recognition of theirsmartphones.

FIGS. 13-18 are schematics illustrating locational tracking, accordingto exemplary embodiments. Once the smartphone 32 is authorized forentry, exemplary embodiments may monitor the movements of the smartphone32. If the visitor's smartphone 32 strays or frolics, a security concernmay develop. Exemplary embodiments, then, may track the smartphone 32 toensure the user stays on route to the meeting 50.

FIG. 13, for example, illustrates room assignments. Here the database 46of meetings may also associate a meeting location 154 to each meeting50. As the reader may realize, conference rooms, offices, beveragerooms, and auditoriums may be uniquely identified by some name and/orlocation. So, when the meeting 50 is scheduled or logged in the database46 of meetings, exemplary embodiments may further store an electronicdatabase association with the corresponding meeting location 154.

FIG. 14 illustrates security routings. Once the location 154 of themeeting 50 is determined (from the database 46 of meetings), thesecurity server 42 may query a database 160 of routings. The database160 of routings stores predetermined building routes 162 from somebeginning location (such as a point of entry 164) to the destination atthe meeting location 154. The database 160 of routings, for example, maystore different routes 162 from the lobby of the building (illustrated,respectively, as reference numerals 22 and 24 in FIG. 1) to the meetinglocation 154 of the scheduled meeting 50. FIG. 14 illustrates thedatabase 160 of routings as being locally stored in the security server42, but some or all of the electronic database entries may be remotelymaintained at some other server or location in the communicationsnetwork (illustrated as reference numeral 106 in FIG. 11). A particularconference room, for example, may have a route 162 along which thevisitor is only permitted to walk or navigate. That is, only certainpaths along particular halls and/or through particular doors areavailable to the visitor. The database 160 of routings may thus storeapproved routes 162 along which employees, tenants, and/or visitors maymove from any point (such as the entry 164) to the final destination atthe meeting location 154.

FIG. 15 illustrates GPS tracking. After the visitor's smartphone 32 isauthorized for entry, the visitor should walk or travel along thepredetermined route 162 to the destination meeting location 154. Afterall, confining the visitor to the predetermined route 162 may helpprevent rogue access to unauthorized locations. Exemplary embodiments,then, may track the visitor's position or progress along thepredetermined route 162. FIG. 15 thus illustrates GPS waypoints 170along which the smartphone 32 may or must report. That is, thepredetermined route 162 may be defined as a series of global positioningsystem information. As the visitor walks the corridors of the building,the visitor's smartphone 32 may continually, periodically, and/orrandomly report its current location 172. FIG. 15 illustrates thesmartphone 32 reporting its current location 172 into the wirelessnetwork 40, which the access device 100 may forward to the securityserver 42. The current location 172, however, may be routed into acellular network for delivery to the network address associated with thesecurity server 42. Regardless, when the security server 42 receives thecurrent location 172, the security server 42 may compare the currentlocation 172 to the GPS waypoints 170 associated with the meetinglocation 154. If the current location 172 matches one of the GPSwaypoints (perhaps within a locational tolerance), then the securityalgorithm 122 may conclude that the visitor's smartphone 32 is on trackand proceeding as authorized. However, if the current location 172reported by the visitor's smartphone 32 fails to match one or any of theGPS waypoints 170, the security algorithm 122 may generate a securitynotification 174. The security notification 174 may be any electronicmessage that warns the visitor to resume the predetermined route 162 tothe destination meeting location 154. The security notification 174 mayroute back to the access device 100 for transmission to the networkaddress assigned to the smartphone 32. However, the securitynotification 174 may be a short message service (SMS) text message thatis sent to the unique cellular identifier 110 of the visitor'ssmartphone 32. The security notification 174 may further include acorrection 176 that puts the visitor back on the predetermined route 162to the destination meeting location 154. Moreover, the security server42 may also copy or forward the security notification 174 to a deviceassociated with a security guard for nearly immediate humanintervention.

FIG. 16 illustrates network tracking. Here exemplary embodiments mayinfer the location of the visitor's smartphone 32 using networkrecognition. As the reader may understand, GPS signals are sometimes notreceived in indoor environments. Exemplary embodiments, then, mayadditionally or alternatively infer the location of the visitor'ssmartphone 32 using network identifiers. FIG. 16 thus illustratesnetwork waypoints 180 along which the smartphone 32 must request accesspermission. That is, the predetermined route 162 may be defined as aseries of network identifiers. For example, as the visitor walks thecorridors of the building, the visitor's smartphone 32 may wirelesslyencounter different wireless fidelity (WI-FI®) networks serving thedifferent floors, hallways, and/or rooms. The visitor's smartphone 32may also detect other identifiers of other networks (such as differentcellular network cells). Regardless, the smartphone 32 may requestaccess permission to each wireless network 40. The corresponding accessdevice 100 may thus notify the security server 42 using the accessnotification 104 (above explained with reference to FIG. 8). FIG. 16,for simplicity, illustrates the network waypoints 180 as a series 182 ofservice set identifiers. Each individual service set identifier (or“SSID”) 184 uniquely identifiers a different WI-FI® network serving someportion of the predetermined route 162 to the destination meetinglocation 154. When the security server 42 receives each accessnotification 104, the access notification 104 may identify thecorresponding SSID 184. The security server 42 may thus compare the SSID184 to the network waypoints 180 associated with the meeting location154. If the SSID 184 matches one of the network waypoints 180, then thesecurity algorithm 122 may conclude that the visitor's smartphone 32 ison track and proceeding as authorized. However, if the SSID 184 fails tomatch one or any of the network waypoints 180, the security algorithm122 may generate the security notification 174 with the correction 176(as earlier explained).

FIG. 17 illustrates a strict comparison. As the security server 42receives each access notification 104, the security server 42 mayrequire a strict sequential match with the network waypoints 180. Thevisitor's smartphone 32, in other words, may be required to traverse thenetwork waypoints 180 in sequential order, from a first entry SSID 190to a final destination SSID 192 serving the destination meeting location154. If the visitor's smartphone 32 strays from the predetermined route162, one of the access notifications 184 will identify an SSID 184 notmatching the approved route 162. The smartphone 32, in other words, isrequesting wireless access to an unauthorized network, thus revealing afrolic or detour. The security algorithm 122 may thus alert security (asearlier explained).

FIG. 18 illustrates timing requirements. Here each network waypoint 180may also have a corresponding timing parameter 200. FIG. 18 thusillustrates each network waypoint 180 as an SSID/time pairing. That is,each network waypoint 180 may be a network/timing pair of valuesassociated with each successive wireless network 40. As the visitor'ssmartphone 32 travels along the predetermined route 162, the securityserver 42 may monitor a speed or time of movement. Each accessnotification 104 may have a timestamp 202 that marks a time of requestedaccess to the wireless network 40 (as identified by the SSID 184). Asthe security server 42 sequentially compares the SSID 184 to the networkwaypoints 180, the security server 42 may also require strict adherenceto each corresponding timing parameter 200. The security server 42, inother words, may initialize a timer 204 with receipt of the accessnotification 104. The timer 204 counts up or down to a final value at areceipt of a next access notification 104 associated with the samesmartphone 32 (e.g., the cellular identifier 110). The timer 204, forexample, may thus count a time in seconds or minutes between successiveaccess notifications 104 sent from different access devices 100 alongthe predetermined route 162. So, not only must each sequential SSID 184match the network waypoints 180, but exemplary embodiments may alsorequire timing compliance between the successive network waypoints 180.The security server 42 may thus compare a current value of the timer 204to the timing parameter 200 associated with a next corresponding networkwaypoint 182 along the predetermined route 162. If the current value ofthe timer 204 is less than or equal to the timing parameter 200, thenthe security algorithm 122 may conclude that the visitor's smartphone 32is on the approved route 162 and on track to arrive on time at the finalmeeting destination location 154. However, if the current value of thetimer 204 exceeds the timing parameter 200, the security algorithm 122may conclude that the visitor's smartphone 32 has strayed from thepredetermined route 162. The security algorithm 122 may thus alertsecurity (as earlier explained).

FIGS. 19-22 are schematics illustrating building services, according toexemplary embodiments. Here exemplary embodiments may coordinate or timevarious building services with respect to the location of the smartphone32. As the smartphone 32 travels along the predetermined route 162 (asrepresented by the GPS current location 172, any of the GPS waypoints170, the SSID 184, and/or any of the network waypoints 180), thesecurity server 42 may thus order up or coordinate various buildingservices at appropriate times and locations. FIG. 19, for example,illustrates a database 210 of services. The database 210 of services isillustrated as a table 212 that associates different locations 214 todifferent services 216. As the reader may understand, one of theservices 216 may be lighting requirements 218 for each differentlocation 214. As the user carries the smartphone 32 through hallways andother areas, lights may need to be activated. So, as the security server42 is informed of the smartphone's location 214 along the route 162, thesecurity server 42 may query the database 210 of services for thecorresponding lighting requirements 218.

Lights may thus be defined. The database 210 of services may thus storeelectronic database associations for the lights that illuminate thedifferent locations 214. Each wireless network 40, for example, may bemapped to the light fixtures 220 and/or lighting loads 222 (such asindividual electrical circuits) illuminating its wireless service area.Whenever the security server 42 receives the access notification 104,the security server 42 may thus query for the SSID 184 and retrieve thelighting requirements 218 for its wireless service area. As FIG. 19further illustrates, electronic database associations may be defined forany GPS coordinates or waypoints along the route 162.

As FIG. 20 illustrates, the lights may be activated. Once the securityserver 42 knows the lighting requirements 218 for the location 214, thesecurity server 42 may send a lighting command 230 into thecommunications network 106 for delivery to the network addressassociated with a lighting controller 232. The lighting controller 232responds by activating, or turning on, the corresponding physical lightfixture 234 and/or the physical electrical load 236. The security server42 may thus coordinate the lights along the predetermined route 162 forsafety and security. Lights may then be deactivated when no mobiledevice requests wireless access to the corresponding wireless servicearea. Lights may also be deactivated after some passage of time.

FIG. 21 illustrates HVAC services. Here exemplary embodiments may alsocoordinate heat or air conditioning with respect to the location 214along the approved route 162. As the reader likely understands, as theuser or visitor travels along the predetermined route 162 (asrepresented by the GPS current location 172, any of the GPS waypoints170, the SSID 184, and/or any of the network waypoints 180), thesecurity server 42 may heat or cool the corresponding physical space orarea. Indeed, the security server 42 may even order up an ambienttemperature within the destination meeting location (illustrated asreference numeral 154 in FIGS. 15-16). The database 210 of services maythus include entries for HVAC settings 240 associated with the location214 along the approved route 162. For example, the security server 42may thus query the database 210 of services for the SSID 184 andretrieve the corresponding HVAC settings 240 (such as a temperature 242and/or humidity 244) associated with the corresponding physical space orarea. The security server 42 may then send an HVAC command 246 into thecommunications network 106 for delivery to the network addressassociated with an HVAC system 248. The security server 42 may evenreceive weather data 249 to further analyze and satisfy the HVACsettings 240 desired for the corresponding physical space or area.

FIG. 22 illustrates other services. Exemplary embodiments may alsocoordinate many other services for the comfort and convenience of theinvitees/attendees. The database 210 of services, for example, may alsohave entries for other services, such as network access 250, equipment252, and vending 254. Continuing with the above examples, the securityserver 42 may query the database 210 of services for the SSID 184 of themeeting location 154. The security server 42 may thus retrieve thecorresponding services 216 defined for that meeting location 214. Thesecurity server 42 may then generate an electronic, packetized serviceorder 256 that routes to a network address of a service provider system258. For example, when each invitee arrives at the destination meetinglocation 154, the security server 42 may arrange or prearrange wirelessnetwork access 250 for each attendee's mobile wireless device. Thesecurity server 42, for example, knows the SSID 184 of the WIFI® networkserving the destination conference room, along with the unique cellularidentifier 110 of each attendee's wireless device (as explained withreference to FIGS. 11-14). The security server 42 may thus pre-authorizeeach attendee's wireless device for wireless service in the destinationconference room. Any wireless access point, in other words, may beinstructed to recognize the unique cellular identifier 110 of eachattendee's wireless device. Each attendee's device thus has immediateaccess to wireless services.

The equipment 252 may also be ordered. Computers, projectors, conferencephone set-up, pens, and whiteboards are just some of the equipment 252that may be pre-ordered, based on the location 214. The meetingorganizer (illustrated as reference numeral 152 in FIG. 12) may thusenter any data or description of the equipment 252 desired for themeeting. The security server 42 may thus pre-arrange arrival and set-upof the equipment 252. As the attendees enter the destination meetinglocation 154, the equipment 252 they need is automatically ordered andwaiting for use.

Vending 254 may also be pre-arranged. The meeting organizer may thusenter or request any food and drink for the meeting. The security server42 may thus issue orders or commands for on-time delivery of food anddrink from some identified vendor. As the attendees enter thedestination meeting location 154, the requested food and drink isautomatically ordered and waiting for consumption.

FIG. 23 is a schematic illustrating elevator summons, according toexemplary embodiments. As the smartphone 32 moves along the pre-approvedroute 162 to the destination meeting location 154, at some pointelevator service may be required. Exemplary embodiments may thus trackthe smartphone's movement and generate elevator commands at appropriatemoments in time or location. FIG. 23, for example, illustrates anelevator command 270 as a data triplet 271 inserted into one of thenetwork waypoints 180. The elevator command 270 identifies whichelevator (elevator number or identifier) is summoned for vertical travelfrom an entry floor to an exit floor. If a building only has oneelevator, then perhaps the elevator command 270 may be simplified to apair of data values. But many buildings may have multiple elevators,perhaps serving different floors. The elevator command (3, 1, 22), forexample, may call or summon “Elevator #3” to “Floor #1” for lift serviceto “Floor #22.” The opposite elevator command (3, 22, 1) would call“Elevator #3” to “Floor #22” for descend service to “Floor #1.” Eachelevator command 270 may thus be generated for insertion into thepre-determined sequential network waypoints 180. As the smartphone 32satisfied each sequential network waypoint 180, the security server 42may summon the corresponding elevator in the sequence. The securityalgorithm 122 may further initialize the timer 204 to count up or downuntil the summons. Exemplary embodiments, then, may insert the elevatorcommand 270 at appropriate positions and/or times in the sequentialnetwork waypoints 180 and/or the sequential GPS waypoints (illustratedas reference numeral 170 in FIG. 15). As the security server 42 tracksthe smartphone 32, the security server 42 may thus read, retrieve,and/or execute the elevator command 270 as one of the sequential steps.The security server 42 may thus generate an elevator instruction 272that is sent into the communications network 106 for delivery to thenetwork address associated with the elevator controller 92. Elevatorservice may thus be summoned to coincide with the current location ofthe smartphone 32.

FIGS. 24-25 are schematics further illustrating the database 70 ofcalendars, according to exemplary embodiments. When the wireless network40 detects the radio presence of the visitor's smartphone 32, the accessdevice 100 sends the access notification 104 (as earlier explained). Thesecurity server 42 may then query the database 70 of calendars for amatching entry. The database 70 of calendars stores different electroniccalendars for the different employees and/or tenants in the building.FIG. 25, for example, illustrates the database 70 of calendars as atable 280 that maps, relates, or associates different electroniccalendars 72 to different invitees 282. As there may be hundreds ofemployees or tenants, the database 70 of calendars may store a memorypointer or network address to an individual person's electronic calendar72. Regardless, when the visitor's smartphone 32 requests access to thewireless network 40, the database 70 of calendars may be searched orqueried for a matching entry. For example, FIG. 25 illustrates thedatabase 70 of calendars storing electronic database associationsbetween electronic calendar entries 72 and their respective invitees282. Whenever a person schedules a meeting or telephone call, forexample, the invitee may be uniquely identified by his or her uniquecellular identifier 110. An appointment in an electronic calendar, inother words, may be arranged or associated with the CTN 112, the IMSI114, and/or the MSISDN 116 of a participant 282.

The security server 42 may authorize entry. Referring back to FIG. 24,when the security server 42 receives the access notification 104, thesecurity server 42 may query the database 70 of calendars for thevisitor's unique cellular identifier 110. If a matching entry isdetermined, the security server 42 may permit physical entry, as thevisitor is scheduled for an appointment with an employee or tenant.Moreover, if the database 70 of calendars identifies the meetinglocation 154, the security server 42 may further retrieve and monitorthe predetermine route 162 to the meeting location 154 (as thisdisclosure explains with reference to FIGS. 14-18 and 23).

FIGS. 26-29 are schematics illustrating historical network tracking,according to exemplary embodiments. Here, historical observances ofwireless detections may be used to infer future actions. That is, auser's habitual usage of the smartphone 32 may be used to predict whereshe will move, and/or what she will do, based on her past movements andwireless network access. For example, as the smartphone 32 repeatedlymoves within the building 24, over time exemplary embodiments may makerecommendations and assumptions, based on habitual observance of itsnetwork usage. Whenever the smartphone 32 is detected at some locationor requesting access to any network, exemplary embodiments may matchthat detection to some past occurrence. In other words, most people arecreatures of habit, so exemplary embodiments may predict our futuremovements and actions based on our historical behaviors.

FIG. 26 illustrates a database 300 of usage. The database 300 of usagetracks historical usage of any user's wireless device 30 (such as thesmartphone 32). The database 300 of usage may store entries related tousage at different times of days and/or at different locations. Wheneverthe smartphone 32 reports its GPS current location 172, for example,exemplary embodiments may query the database 300 of usage for historicalusage at that same location. The database 300 of usage may thus log eachcurrent location 172 reported by the smartphone 32. As the smartphone 32moves within the building 24, the smartphone 32 may repeatedly send itscurrent location 172 (such as GPS information) to the security server42. The security server 42 may then log these locational reports in thedatabase 300 of usage. The database 300 of usage is illustrated as beinglocally stored within the security server 42, but any of the databaseentries may be remotely maintained at other network-accessible locationsor servers. FIG. 26 illustrates the database 300 of usage as a table 302that electronically maps, relates, or associates the cellular identifier110 to different location reports. That is, each time the smartphone 32reports its current location 172, the database 300 of usage may add anentry for the unique cellular identifier 110, the reported currentlocation 172, and a date and time 304 of the report. Over time, then,the database 300 of usage may store long-term records of the movementsof the smartphone 32 within the building 24.

FIG. 27 illustrates historical network usage. Each time the smartphone32 requests access to the wireless network 40, the corresponding accessdevice 100 sends the packetized access notification 104 to alert thesecurity server 42 (as this disclosure earlier explained). The securityserver 42 may thus instruct the database 300 of usage to log the accessnotification 104, perhaps also with the date and time 304. That is, eachtime the smartphone 32 requests wireless access to the wireless network40, the database 300 of usage may add an entry for the unique cellularidentifier 110, the service set identifier (“SSID”) 184 of the wirelessfidelity (“WI-FI®”) network 40, and the date and time 304 of therequest. As FIG. 27 illustrates, the database 300 of usage may merelylog the timestamp 202 reported in the access notification 104, or thedatabase 300 of usage may log some other measure of time (such asreceipt of the access notification 104). Regardless, over time thedatabase 300 of usage reveals a comprehensive long-term centralrepository of network access requested by the smartphone 32.

The security server 42 may thus infer future entries from the historicalinformation. The security server 42, for example, may query the database300 of usage for any search terms and retrieve matching historicalentries. The security server 42, as an example, may query for historicalentries associated with the cellular identifier 110. The security server42 may thus retrieve historical locations or networks logged in thedatabase 300 of usage. Indeed, the security server 42 may even query forhistorical entries having the same or approximate date and time 304. Thesecurity server 42 may thus retrieve historical entries that match thesame or similar day, time, current location 172, or network SSID 184.

FIG. 28 illustrates locational prediction. Whenever the smartphone 32reports its current location 172, the security server 42 may predict orinfer a future location 310. For example, the security server 42 mayquery for a series or sequence of entries having about the same location172 and/or the same date and time 304. For example, if one or more ofthe smartphone's recent locational reports match one or more historicalentries, then the security algorithm 122 may infer that the smartphone32 is moving along a path historically observed. That is, the smartphone32 is being carried along a familiar route to a historical destinationpreviously logged in the database 300 of usage. In other words, if arecent string or sequence of locational reports matches some sequence ofhistorical entries, then the security algorithm 122 may conclude thatthe smartphone 32 is traveling along the same route to the samedestination. If the smartphone 32 reports the same current locations 172within a ten minute (10 min.) window of time as historically seen, thesecurity server 42 may thus predict or infer that the smartphone 32 willhave the future location 310 that matches at least one of the historicalentries in the same series. As one example, if the smartphone's mostrecent five (5) location reports match some historical observance in thedatabase 300 of usage, then the security server 42 may predict thesmartphone's future location 310 will match the next historical sixth(6^(th)) entry in the same historical sequence. The security server 42may thus query for any search terms and retrieve one or multiplehistorical entries that match recent locational reports. As most peopleare creatures of habit, the security server 42 may thus predict thefuture location 310 of the smartphone 32 based on historicalobservances.

FIG. 29 illustrates network prediction. As the database 300 of usage mayalso log historical network requests, exemplary embodiments may predictor infer a future network 312. For example, the security algorithm 122may predict the smartphone's access request to a wireless fidelity(“WI-FI®”) network, based on the historical entries in the database 300of usage. The security server 42 may query for a series or sequence ofentries having one or more matching SSID 184 entries and/or about thesame date and time 304. For example, if one or more of the recent accessnotifications 104 match one or more historical entries, then thesecurity algorithm 122 may infer that the smartphone 32 is requestingaccess permissions along a path historically observed. In other words,if a recent string or sequence of access notifications 104 matches somesequence of historical entries, then the security algorithm 122 mayconclude that the smartphone 32 is requesting wireless access ashistorically seen. If a string or sequence 314 of the accessnotifications 104 match historical entries within a ten minute (10 min.)window 316 of time, the security server 42 may thus predict or inferthat the smartphone 32 will request access to a next entry historicallyobserved in the same series. As FIG. 29 illustrates, if the recentaccess notifications 104 report the sequence 314 “SSID2, SSID3, SSID4,SSID3,” then the security algorithm 122 may retrieve the next entry inthe same sequence 314 and predict that the smartphone 32 will nextrequest access to “SSID9.” The security algorithm 122, in other words,infers the future network 312 as the next entry in the matching sequence314. The security algorithm 122 may thus pre-arrange wireless access,elevator service, lighting, and other services based on this prediction.

FIG. 30 is another schematic illustrating network tracking, according toexemplary embodiments. Here exemplary embodiments may track usage oraccess requests to any networking environment. As FIG. 30 illustrates,whenever the smartphone 32 requests access to any wireless network 40,the access notification 104 may report the networking details. Theaccess notification 104, for example, may report a radio frequency 320and/or bitrate 322 of communication between the smartphone 32 and someother device (such as the access device 100). The timestamp 202 may befurther added. When the security server 42 receives the accessnotification 104, the security algorithm 122 may thus log these detailsin the database 300 of usage. For example, the radio frequency 320and/or bitrate 322 may allow the security algorithm 122 to log whetherthe wireless network 40 operates at cellular frequencies or WIFI®frequencies.

Other networking environments may also be tracked. When the securityserver 42 receives the access notification 104, the radio frequency 320and/or the bitrate 322 may reveal near-field communications (“NFC”)and/or radio frequency identification (“RFID”) communications. Forexample, when the smartphone 32 participates in near-fieldcommunication, the access notification 104 may additionally oralternatively report an initiator device 324 and a target device 326.Likewise, the access notification 104 may also detail unique radiofrequency identification tags and readers. When the security server 42receives the access notification 104, the security algorithm 122 maythus log these details in the database 300 of usage. Over time, then,the database 300 of usage contains historical entries detailing the NFCand RFID transactions involving the smartphone 32. If any currenttransaction matches some historical entry, the security algorithm 122may predict or infer future actions and/or locations, based on thematch. The security algorithm 122 may thus pre-arrange wireless access,elevator service, lighting, and other services based on this prediction.

FIG. 31 is a schematic illustrating an overall database scheme,according to exemplary embodiments. Here the security server 42 mayaccess any of the databases (illustrated as reference numerals 44, 46,70, 160, 210, and 300) to authorize access, to coordinate services, andto predict actions, as this disclosure explains. The databases may beindividually maintained or grouped together, depending on networking,processing, and storage capabilities.

FIG. 32 is a schematic illustrating cancellations, according toexemplary embodiments. Even though the security server 42 may haveauthorized access, coordinated services, and/or predicted actions,sometimes cancellations are determined. For example, a meeting organizermay simply cancel a scheduled meeting in the database 46 of meetings.This cancellation 340 may then trickle down and affect access, services,and predictions. For example, if the cancellation 340 is determined inthe database 46 of meetings, the security server 42 may disperse thatcancellation 340. The invitees' devices to the now-canceled meeting maybe notified (perhaps using the notification message 80 illustrated inFIG. 6). Entry authorization for the invitees' devices may be canceledby removal from the database 46 of meetings and/or removal from thedatabase 70 of calendars. The entry instruction (illustrated asreference numeral 86 in FIG. 7) may be canceled, thus stopping orceasing any entry process. The elevator instruction (illustrated asreference numeral 272 in FIG. 23) may be canceled, thus removing anysummons for elevators. Likewise, any retrieval and/or analysis of routesin the database 160 of routings may be canceled or aborted. Anyretrieval and/or electronic order of services in the database 210 ofservices may also be canceled or aborted. Moreover, electronicnotifications of the cancelation 340 may be sent to service providers(such as contractors and vendors). Any historical analysis of entries inthe database 300 of usage may be halted or aborted. The cancelation 340may thus electronically cancel any reservation for a conference room,HVAC needs, and lighting requirements.

FIG. 33 is a schematic illustrating conferencing activities, accordingto exemplary embodiments. Here exemplary embodiments may arrange andset-up a teleconference call and/or a telepresence video call betweenthe visitor's smartphone 32 and other participants. When the visitorarrives, the visitor's smartphone 32 requests wireless access (asearlier explained). The security server 42 may thus use the uniquecellular identifier 110 to retrieve any meeting entries in the database46 of meetings and/or in the database 70 of calendars. The securityserver 42 may arrange a conference room and/or an office or desk for thevisitor, in response to a matching entry. The security server 42 mayalso automatically set-up a teleconference call or a videoconferencecall to the meeting invitee devices retrieved from the database 46 ofmeetings and/or the database 70 of calendars. The security server 42 mayalso concomitantly arrange video cameras, whiteboards, beverages,lighting, and other services (perhaps revealed by the database 210 ofservices, as previously explained).

FIGS. 34-35 are flowcharts illustrating an algorithm for accessauthorization, according to exemplary embodiments. A unique cellularidentifier 110 is received (Block 350) and the security server 42 isnotified (Block 352). A database is queried for the cellular identifier110 (Block 354). Physical access to a secure area is granted, based on amatching entry in the database (Block 356). The electronic lock 90 maybe activated to permit entry (Block 358). The electronic notificationmessage 80 may be sent to a meeting organizer and/or other invitees,thus alerting to the arrival and access of the user associated with thecellular identifier (Block 360). The location 154 of the meeting mayalso be determined (Block 362).

The flowchart continues with FIG. 35. Once the location 154 is known,the corresponding route 162 retrieved (Block 364). The elevator 94 maybe summoned (Block 366). The corresponding services 216 may also beretrieved (Block 368). Historical usage associated with the cellularidentifier 110 is retrieved (Block 370). The future location 310 (Block372) and/or the future network 312 (Block 374) may be predicted.Physical facilities are allocated based on the cellular identifier 110(Block 376).

FIG. 36 is a schematic illustrating still more exemplary embodiments.FIG. 36 is a more detailed diagram illustrating a processor-controlleddevice 400. As earlier paragraphs explained, exemplary embodiments maypartially or entirely operate in any mobile or stationaryprocessor-controlled device. FIG. 36, then, illustrates the securityalgorithm 122 stored in a memory subsystem of the processor-controlleddevice 400. One or more processors communicate with the memory subsystemand execute either, some, or all applications. Because theprocessor-controlled device 400 is well known to those of ordinary skillin the art, no further explanation is needed.

FIG. 37 depicts other possible operating environments for additionalaspects of the exemplary embodiments. FIG. 37 illustrates the securityalgorithm 122 operating within various other processor-controlleddevices 400. FIG. 37, for example, illustrates that the securityalgorithm 122 may entirely or partially operate within a set-top box(“STB”) (402), a personal/digital video recorder (PVR/DVR) 404, a GlobalPositioning System (GPS) device 408, an interactive television 410, atablet computer 412, or any computer system, communications device, orprocessor-controlled device utilizing the processor and/or a digitalsignal processor (DP/DSP) 414. The device 400 may also include watches,radios, vehicle electronics, clocks, printers, gateways,mobile/implantable medical devices, and other apparatuses and systems.Because the architecture and operating principles of the various devices400 are well known, the hardware and software componentry of the variousdevices 400 are not further shown and described.

Exemplary embodiments may be physically embodied on or in acomputer-readable storage medium. This computer-readable medium, forexample, may include CD-ROM, DVD, tape, cassette, floppy disk, opticaldisk, memory card, memory drive, and large-capacity disks. Thiscomputer-readable medium, or media, could be distributed toend-subscribers, licensees, and assignees. A computer program productcomprises processor-executable instructions for automatic secure access,as the above paragraphs explained.

While the exemplary embodiments have been described with respect tovarious features, aspects, and embodiments, those skilled and unskilledin the art will recognize the exemplary embodiments are not so limited.Other variations, modifications, and alternative embodiments may be madewithout departing from the spirit and scope of the exemplaryembodiments.

1. A method, comprising: receiving, by a server, an identifierassociated with a wireless device; determining, by the server, adestination associated with the wireless device; querying, by theserver, an electronic database for the destination associated with thewireless device, the electronic database electronically associatingwireless networks to destinations including the destination associatedwith the wireless device; identifying, by the server, a wireless networkof the wireless networks in the electronic database that iselectronically associated with the destination associated with thewireless device; and sending, by the server, an entry instruction viathe wireless network that authorizes an access to the destination. 2.The method of claim 1, further comprising receiving a request to accessthe wireless network.
 3. The method of claim 1, further comprisingdetermining a user associated with the wireless device.
 4. The method ofclaim 1, further comprising determining a date associated with theaccess to the destination.
 5. The method of claim 1, further comprisingdetermining a time associated with the access to the destination.
 6. Themethod of claim 1, further comprising determining a calendar associatedwith the wireless device.
 7. The method of claim 1, further comprisingsending a notification associated with the access to the destination. 8.A system, comprising: a processor; and a memory device, the memorydevice storing instructions, the instructions when executed causing theprocessor to perform operations, the operations comprising: receiving anidentifier associated with a wireless device; determining a destinationassociated with the wireless device; querying an electronic database forthe destination associated with the wireless device, the electronicdatabase electronically associating wireless networks to destinationsincluding the destination associated with the wireless device;identifying a wireless network of the wireless networks in theelectronic database that is electronically associated with thedestination associated with the wireless device; and sending an entryinstruction via the wireless network that authorizes an access to thedestination.
 9. The system of claim 8, wherein the operations furthercomprise receiving a request to access the wireless network.
 10. Thesystem of claim 8, wherein the operations further comprise determining auser associated with the wireless device.
 11. The system of claim 8,wherein the operations further comprise determining a date associatedwith the access to the destination.
 12. The system of claim 8, whereinthe operations further comprise determining a time associated with theaccess to the destination.
 13. The system of claim 8, wherein theoperations further comprise determining a calendar associated with thewireless device.
 14. The system of claim 8, wherein the operationsfurther comprise sending a notification associated with the access tothe destination.
 15. A memory device storing instructions that whenexecuted cause a processor to perform operations, the operationscomprising: receiving an identifier associated with a wireless device;determining a destination associated with the wireless device; queryingan electronic database for the destination associated with the wirelessdevice, the electronic database electronically associating wirelessnetworks to destinations including the destination associated with thewireless device; identifying a wireless network of the wireless networksin the electronic database that is electronically associated with thedestination associated with the wireless device; and sending an entryinstruction via the wireless network that authorizes an access to thedestination.
 16. The memory device of claim 15, wherein the operationsfurther comprise receiving a request to access the wireless network. 17.The memory device of claim 15, wherein the operations further comprisedetermining a user associated with the wireless device.
 18. The memorydevice of claim 15, wherein the operations further comprise determininga date associated with the access to the destination.
 19. The memorydevice of claim 15, wherein the operations further comprise determininga time associated with the access to the destination.
 20. The memorydevice of claim 15, wherein the operations further comprise determininga calendar associated with the wireless device.